Description

This PR aligns the template with latest Expo developments that we had to until now substituted through custom Github Actions.

1. we are now setting build number from Expo remote config instead of Github variable BUILD_NUMBER that was used for that purpose until now.
2. we are deprecating and removing copying of Github env variables to eas.json on both build and OTA update in favour of using Expo environment variables.
   By making these changes we want to align more to a standard Expo workflows and remove complexity from our github actions that doesn't have to be there.

There is a mapping that should be just temporary until we fully align our environment names. For now all github actions environment names are mapped from our names to EAS names, dev -> development, staging -> preview, production -> production. This is done automatically in build and update actions. Just keep this in mind when you are setting environment variables directly in EAS dashboard.

How to migrate:

• copy over all contents of .github/actions and .github/workflows folder from the template into your project
• BUILD NUMBER SETUP
  • make sure that the BUILD_NUMBER env variable in your projects Github repo is synced with the remote value in Expo for both staging and production profiles. This is done through eas build:version:set --profile command.
  • delete buildNumber and all of its uses from app.config.ts.
  • make sure that in eas.json "autoIncrement": true is set for staging and production
• ENV VARIABLES SETUP
  • make sure your env variables from Github are synced with your EAS dashboard, you can do this either through the EAS dashboard UI or through the CLI.
  • set correct environment in your eas.json. You can look into the template for reference.

Related Tickets/Issues